fix: ensure CI fails when pytest fails by adding pipefail#339
Open
lauty95 wants to merge 3 commits intoversion-15from
Open
fix: ensure CI fails when pytest fails by adding pipefail#339lauty95 wants to merge 3 commits intoversion-15from
lauty95 wants to merge 3 commits intoversion-15from
Conversation
📝 Draft Changelog EntryChangelogFixed an issue where the continuous integration system would not properly report test failures. The CI pipeline now correctly halts when tests fail, ensuring that broken code is not inadvertently merged. This changelog entry was automatically generated by the Changelog Generator Action. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bash pipelines (|) return the exit code of the last command by default. By enabling set -o pipefail, the pipeline fails if any command fails.
This ensures that the workflow correctly fails when pytest fails.
This behavior is already present in the
mobile_v15branch, but was missing in the current target branch.